ci: Hook up release-module

In the future, the module will automate uploading the release
tarball. We already use the CI pipeline to generate the tarball,
so it's easy to hook up the module and provide some testing
before the module goes into production.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3340>
(cherry picked from commit 1fbfb93cbd90069f0923e829a8180fb2050fabf9)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 44bb138f9ca690cc3f270ec90670e442acdf6dd0..cee18a35353a2f7c554cabe29f5843cc91a77fb0 100644 (file)
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -2,6 +2,8 @@ include:
   - remote: 'https://gitlab.gnome.org/GNOME/citemplates/raw/HEAD/flatpak/flatpak_ci_initiative.yml'
   - remote: 'https://gitlab.freedesktop.org/freedesktop/ci-templates/-/raw/057b052e682d8e5a20c1eb2dd60d5b87d2b56856/templates/fedora.yml'
   - remote: 'https://gitlab.freedesktop.org/freedesktop/ci-templates/-/raw/34f4ade99434043f88e164933f570301fd18b125/templates/ci-fairy.yml'
+  - project: 'Infrastructure/openshift-images/gnome-release-service'
+    file: '/ci-templates/release-module.yml'
 
 stages:
   - pre_review
@@ -311,6 +313,14 @@ dist-tarball:
   rules:
     - if: '$CI_COMMIT_TAG'
 
+release-module:
+  stage: deploy
+  needs:
+    - dist-tarball
+  extends: .release-module
+  rules:
+    - if: '$CI_COMMIT_TAG'
+
 reference:
   stage: docs
   needs: ["build"]